System and method for providing a graphical user interface

ABSTRACT

A server comprises a communications module; a processor coupled with the communications module; and a memory coupled to the processor and storing processor-executable instructions which, when executed by the processor, configure the processor to obtain transfer records identifying value transfers associated with an account of a user, the transfer records including a transfer amount, a transfer date and a transfer descriptor; group the transfer records based on predefined criteria; within at least one group of the transfer records, identify one or more representative transfer records based at least on stored selection criteria; obtain an image associated with at least one of the representative transfer records; and send, via the communications module and to a computing device associated with the user, a transfer record summary interface, the transfer record summary interface including the image associated with the at least one representative transfer record.

TECHNICAL FIELD

The present application relates to graphical user interfaces and, moreparticularly, to systems and methods for providing a graphical userinterface.

BACKGROUND

Graphical user interfaces are often used to display informationassociated with transfer records associated with an account. Forexample, a graphical user interface may display information associatedwith transfer records in the form of a list or spreadsheet.

Graphical user interfaces and other such interfaces can result in anunnecessary waste in bandwidth and computer processing power as userinteraction with the graphical user interface results in data exchangesbetween the computing device displaying the graphical user interface andthe computer server providing the graphical user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are described in detail below, with reference to thefollowing drawings:

FIG. 1 is a schematic operation diagram illustrating an operatingenvironment of an example embodiment;

FIG. 2 is a simplified schematic diagram showing components of acomputing device;

FIG. 3 is a high-level schematic diagram of an example computing device;

FIG. 4 shows a simplified organization of software components stored ina memory of the example computing device of FIG. 3;

FIG. 5 is a flowchart showing operations performed by a server inproviding a transfer record summary interface according to anembodiment;

FIG. 6 is a flowchart showing operations performed by a server inobtaining an image from an image library according to an embodiment;

FIG. 7 is a flowchart showing operations performed by a server inobtaining an image from an application programming interface accordingto an embodiment;

FIG. 8 is a flowchart showing operations performed by a server indetermining that an image cannot be found for a particular transferrecord according to an embodiment;

FIG. 9 is an example screen of a transfer record summary interfaceaccording to an embodiment;

FIG. 10 is a flowchart showing operations performed by a server insending data for all transfer records within a group represented by aselected image according to an embodiment;

FIG. 11 is an example screen of a transfer record summary interfaceaccording to an embodiment;

FIG. 12 is an example screen of a transfer record summary interfaceaccording to an embodiment;

FIG. 13 is an example screen of a transfer record summary interfaceaccording to an embodiment;

FIG. 14 is an example screen of a transfer record summary interfaceaccording to an embodiment;

FIG. 15 is an example screen of a transfer record summary interfaceaccording to an embodiment;

FIG. 16 is a flowchart showing operations performed by a server inproviding an updated transfer record summary interface according to anembodiment;

FIG. 17 is an example screen of a transfer record summary interfaceaccording to an embodiment; and

FIG. 18 is an example screen of a transfer record summary interfaceaccording to an embodiment.

Like reference numerals are used in the drawings to denote like elementsand features.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

Accordingly, in one aspect there is provided a server comprising acommunications module; a processor coupled with the communicationsmodule; and a memory coupled to the processor and storingprocessor-executable instructions which, when executed by the processor,configure the processor to obtain transfer records identifying valuetransfers associated with an account of a user, the transfer recordsincluding a transfer amount, a transfer date and a transfer descriptor;group the transfer records based on predefined criteria; within at leastone group of the transfer records, identify one or more representativetransfer records based at least on stored selection criteria; obtain animage associated with at least one of the representative transferrecords; and send, via the communications module and to a computingdevice associated with the user, a transfer record summary interface,the transfer record summary interface including the image associatedwith the at least one representative transfer record.

In one or more embodiments, the image is obtained from one of anapplication programming interface (API) and an image library stored onthe computing device.

In one or more embodiments, the image is obtained from the image librarystored on the computing device and the processor-executableinstructions, when executed by the processor, further configure theprocessor to obtain permission to access the image library stored on thecomputing device; and associate one of the images within the imagelibrary to one of the representative transfer records based on acomparison of the representative transfer record and metadata of theassociated image.

In one or more embodiments, the processor-executable instructions, whenexecuted by the processor, further configure the processor to receive,via the communications module and from the computing device, a signalindicating a selection of one of the images; obtain all transfer recordsfor the group represented by the selected image; and send, via thecommunications module and to the computing device, all transfer recordsfor the group represented by the selected image.

In one or more embodiments, the processor-executable instructions, whenexecuted by the processor, further configure the processor to tag atleast one of the transfer records with a tag based on the transferdescriptor; and obtain the image based on the tag.

In one or more embodiments, the processor-executable instructions, whenexecuted by the processor, further configure the processor to for atleast one representative transfer record, identify a merchant based onthe transfer descriptor; and obtain the image associated with the atleast one representative transfer record based at least on theidentified merchant, the image including at least one of an image of themerchant, an image of a logo associated with the merchant, an image ofan item offered by the merchant, an image based on a type of themerchant or an image based on a location of the merchant.

In one or more embodiments, the processor-executable instructions, whenexecuted by the processor, further configure the processor to determinethat an image cannot be obtained for a particular representativetransfer record; remove the particular representative transfer record asbeing the representative transfer record for a particular group oftransfer records; and identify another transfer record as beingrepresentative for the particular group of transfer records based atleast on the stored selection criteria.

In one or more embodiments, the transfer record summary interfaceincludes an option to adjust the predefined criteria and theprocessor-executable instructions, when executed by the processor,further configure the processor to receive, via the communicationsmodule and from the computing device, a signal indicating that the userhas adjusted the predefined criteria; group transfer records based onthe updated predefined criteria; within at least one group of transferrecords, identify one or more transfer records as being representativebased at least on the stored selection criteria; for at least onerepresentative transfer record that does not have an associated image,obtain an image; and send, via the communications module and to thecomputing device associated with the user, an updated transfer recordsummary interface, the updated transfer record summary interfaceincluding the image associated with the at least one representativetransfer record.

In one or more embodiments, the predefined criteria includes aparticular period of time.

In one or more embodiments, the stored selection criteria includes atleast one of the transfer amount or the transfer descriptor.

According to another aspect there is provided a method comprisingobtaining transfer records identifying value transfers associated withan account of a user, the transfer records including a transfer amount,a transfer date and a transfer descriptor; grouping the transfer recordsbased on predefined criteria; within at least one group of the transferrecords, identifying one or more representative transfer records basedat least on stored selection criteria; obtaining an image associatedwith at least one of the representative transfer records; and sending,via a communications module and to a computing device associated withthe user, a transfer record summary interface, the transfer recordsummary interface including the image associated with the at least onerepresentative transfer record.

In one or more embodiments, the image is obtained from one of anapplication programming interface (API) and an image library stored onthe computing device.

In one or more embodiments, the image is obtained from the image librarystored on the computing device and the method further comprisesobtaining permission to access the image library stored on the computingdevice; and associating one of the images within the image library toone of the representative transfer records based on a comparison of therepresentative transfer record and metadata of the associated image.

In one or more embodiments, the method further comprises receiving, viathe communications module and from the computing device, a signalindicating a selection of one of the images; obtaining all transferrecords for the group represented by the selected image; and sending,via the communications module and to the computing device, all transferrecords for the group represented by the selected image.

In one or more embodiments, the method further comprises tagging atleast one of the transfer records with a tag based on the transferdescriptor; and obtaining the image based on the tag.

In one or more embodiments, the method further comprises for at leastone representative transfer record, identifying a merchant based on thetransfer descriptor; and obtaining the image associated with the atleast one representative transfer record based at least on theidentified merchant, the image including at least one of an image of themerchant, an image of a logo associated with the merchant, an image ofan item offered by the merchant, an image based on a type of themerchant or an image based on a location of the merchant.

In one or more embodiments, the method further comprises determiningthat an image cannot be obtained for a particular representativetransfer record; removing the particular representative transfer recordas being the representative transfer record for a particular group oftransfer records; and identifying another transfer record as beingrepresentative for the particular group of transfer records based atleast on the stored selection criteria.

In one or more embodiments, the transfer record summary interfaceincludes an option to adjust the predefined criteria and the methodfurther comprises receiving, via the communications module and from thecomputing device, a signal indicating that the user has adjusted thepredefined criteria; grouping transfer records based on the updatedpredefined criteria; within at least one group of transfer records,identifying one or more transfer records as being representative basedat least on the stored selection criteria; for at least onerepresentative transfer record that does not have an associated image,obtaining an image; and sending, via the communications module and tothe computing device, an updated transfer record summary interface, theupdated transfer record summary interface including the image associatedwith the at least one representative transfer record.

In one or more embodiments, the stored selection criteria includes atleast one of the transfer amount and the transfer descriptor.

According to another aspect there is provided a non-transitory computerreadable storage medium comprising computer-executable instructionswhich, when executed, configure a processor to obtain transfer recordsidentifying value transfers associated with an account of a user, thetransfer records including a transfer amount, a transfer date and atransfer descriptor; group the transfer records based on predefinedcriteria; within at least one group of the transfer records, identifyone or more representative transfer records based at least on storedselection criteria; obtain an image associated with at least one of therepresentative transfer records; and send, via the communications moduleand to a computing device associated with the user, a transfer recordsummary interface, the transfer record summary interface including theimage associated with the at least one representative transfer record.

Other aspects and features of the present application will be understoodby those of ordinary skill in the art from a review of the followingdescription of examples in conjunction with the accompanying figures.

In the present application, the term “and/or” is intended to cover allpossible combinations and sub-combinations of the listed elements,including any one of the listed elements alone, any sub-combination, orall of the elements, and without necessarily excluding additionalelements.

In the present application, the phrase “at least one of . . . or . . . ”is intended to cover any one or more of the listed elements, includingany one of the listed elements alone, any sub-combination, or all of theelements, without necessarily excluding any additional elements, andwithout necessarily requiring all of the elements.

FIG. 1 is a schematic operation diagram illustrating an operatingenvironment of an example embodiment. As shown, the system 100 includesa computing device 110 and a server 120 coupled to one another through anetwork 130, which may include a public network such as the Internetand/or a private network. The computing device 110 and the server 120may be in geographically disparate locations. Put differently, thecomputing device 110 and the server 120 may be located remote from oneanother.

The server 120 is a computer system. The server 120 may be associatedwith an institution and may be a financial institution server. Theserver 120 may maintain a database that includes various transferrecords associated with accounts of various customers or users. Atransfer record may, for example, identify value transfers such astransactions made by the user. Each value transfer may be a valuetransfer made by the user using, for example, a credit card or a debitcard linked to the account. The transfer records may include a transferamount, a transfer date and a transfer descriptor. The transferdescriptor may include a name of a merchant and may include a locationsuch as for example a city or country identifying where the transfer wasinitiated.

Although not shown, the server 120 may communicate with one or moreapplication programming interfaces (APIs) which allows the server 120 torequest and obtain data such as for example images via the network 130.

The computing device 110 may take a variety of forms such as asmartphone, a tablet computer, a wearable computer such as ahead-mounted display or smartwatch, a laptop or desktop computer, or acomputing device of another type.

The computing device 110 is adapted to present a graphical userinterface that allows for communication with the server 120. Forexample, the computing device 110 may be adapted to receive, from theserver 120, a transfer record summary interface that includes one ormore images.

The network 130 is a computer network. In some embodiments, the network130 may be an internetwork such as may be formed of one or moreinterconnected computer networks. For example, the network 130 may be ormay include an Ethernet network, an asynchronous transfer mode (ATM)network, a wireless network, a telecommunications network, or the like.

FIG. 1 illustrates an example representation of components of the system100. The system 100 can, however, be implemented differently than theexample of FIG. 1. For example, various components that are illustratedas separate systems in FIG. 1 may be implemented on a common system. Byway of further example, the functions of a single component may bedivided into multiple components.

FIG. 2 is a simplified schematic diagram showing component of anexemplary computing device 200. Computing device 110 may be of the sametype as computing device 200. The computing device 200 may includemodules including, as illustrated, for example, one or more displays210, an image capture module 220, a sensor module 230, and a computerdevice 240.

The one or more displays 210 are a display module. The one or moredisplays 210 are used to display screens of a graphical user interfacethat may be used, for example, to communicate with the server 120 (FIG.1). The one or more displays 210 may be internal displays of thecomputing device 200 (e.g., disposed within a body of the computingdevice).

The image capture module 220 may be or may include a camera. The imagecapture module 220 may be used to obtain image data, such as images. Theimage capture module 220 may be or may include a digital image sensorsystem as, for example, a charge coupled device (CCD) or a complementarymetal-oxide-semiconductor (CMOS) image sensor.

The sensor module 230 may be a sensor that generates sensor data basedon a sensed condition. By way of example, the sensor module 230 may beor include a location subsystem which generates location data indicatinga location of the computing device 200. The location may be the currentgeographic location of the computing device 200. The location subsystemmay be or include any one or more of a global positioning system (GPS),an inertial navigation system (INS), a wireless (e.g., cellular)triangulation system, a beacon-based location system (such as aBluetooth low energy beacon system), or a location subsystem of anothertype.

The computer device 240 is in communication with the one or moredisplays 210, the image capture module 220, and the sensor module 230.The computer device 240 may be or may include a processor which iscoupled to the one or more displays 210, the image capture module 220,and/or the sensor module 230.

Referring now to FIG. 3, a high-level operation diagram of an examplecomputer device 300 is shown. In some embodiments, the computer device300 may be exemplary of the computer device 240 (FIG. 2) and the server120.

The example computer device 300 includes a variety of modules. Forexample, as illustrated, the example computer device 300 may include aprocessor 310, a memory 320, a communications module 330, and/or astorage module 340. As illustrated, the foregoing example modules of theexample computer device 300 are in communication over a bus 350.

The processor 310 is a hardware processor. The processor 310 may, forexample, be one or more ARM, Intel x86, PowerPC processors or the like.

The memory 320 allows data to be stored and retrieved. The memory 320may include, for example, random access memory, read-only memory, andpersistent storage. Persistent storage may be, for example, flashmemory, a solid-state drive or the like. Read-only memory and persistentstorage are a non-transitory computer-readable storage medium. Acomputer-readable medium may be organized using a file system such asmay be administered by an operating system governing overall operationof the example computer device 300.

The communications module 330 allows the example computer device 300 tocommunicate with other computer or computing devices and/or variouscommunications networks. For example, the communications module 330 mayallow the example computer device 300 to send or receive communicationssignals. Communications signals may be sent or received according to oneor more protocols or according to one or more standards. For example,the communications module 330 may allow the example computer device 300to communicate via a cellular data network, such as for example,according to one or more standards such as, for example, Global Systemfor Mobile Communications (GSM), Code Division Multiple Access (CDMA),Evolution Data Optimized (EVDO), Long-term Evolution (LTE) or the like.Additionally or alternatively, the communications module 330 may allowthe example computer device 300 to communicate using near-fieldcommunication (NFC), via Wi-Fi™, using Bluetooth™ or via somecombination of one or more networks or protocols. In some embodiments,all or a portion of the communications module 330 may be integrated intoa component of the example computer device 300. For example, thecommunications module may be integrated into a communications chipset.In some embodiments, the communications module 330 may be omitted suchas, for example, if sending and receiving communications is not requiredin a particular application.

The storage module 340 allows the example computer device 300 to storeand retrieve data. In some embodiments, the storage module 340 may beformed as a part of the memory 320 and/or may be used to access all or aportion of the memory 320. Additionally or alternatively, the storagemodule 340 may be used to store and retrieve data from persisted storageother than the persisted storage (if any) accessible via the memory 320.In some embodiments, the storage module 340 may be used to store andretrieve data in a database. A database may be stored in persistedstorage. Additionally or alternatively, the storage module 340 mayaccess data stored remotely such as, for example, as may be accessedusing a local area network (LAN), wide area network (WAN), personal areanetwork (PAN), and/or a storage area network (SAN). In some embodiments,the storage module 340 may access data stored remotely using thecommunications module 330. In some embodiments, the storage module 340may be omitted and its function may be performed by the memory 320and/or by the processor 310 in concert with the communications module330 such as, for example, if data is stored remotely. The storage modulemay also be referred to as a data store.

Software comprising instructions is executed by the processor 310 from acomputer-readable medium. For example, software may be loaded intorandom-access memory from persistent storage of the memory 320.Additionally or alternatively, instructions may be executed by theprocessor 310 directly from read-only memory of the memory 320.

FIG. 4 depicts a simplified organization of software components storedin the memory 320 of the example computer device 300 (FIG. 3). Asillustrated, these software components include an operating system 400and an application 410.

The operating system 400 is software. The operating system 400 allowsthe application 410 to access the processor 310 (FIG. 3), the memory320, and the communications module 330 of the example computer device300 (FIG. 3). The operating system 400 may be, for example, Google™Android™, Apple™ iOS™, UNIX™, Linux™, Microsoft™ Windows™, Apple OSX™ orthe like.

The application 410 adapts the example computer device 300, incombination with the operating system 400, to operate as a deviceperforming a particular function. For example, the application 410 maycooperate with the operating system 400 to adapt a suitable embodimentof the example computer device 300 to operate as the computer device 240(FIG. 2) and/or the server 120.

While a single application 410 is illustrated in FIG. 3, in operationthe memory 320 may include more than one application 410 and differentapplications 410 may perform different operations. For example, in atleast some embodiments in which the computer device 300 is functioningas the computing device 110, the applications 410 may include a bankingapplication. The banking application may be configured for securecommunications with the server 120 and may provide various bankingfunctions such as, for example, the ability to display a quantum ofvalue in one or more transfer records (e.g. display balances), configuretransfers of data (e.g. bill payments and other transfers), configurebudgeting tools, display a graphical user interface such as for examplea transfer record summary interface, and account management functions.

By way of further example, in at least some embodiments in which thecomputer device 300 functions as the computing device 110, theapplications 410 may include a web browser, which may also be referredto as an Internet browser. In at least some such embodiments, the server120 may be a web server that may serve one or more of the interfacesdescribed herein. The web server may cooperate with the web browser andmay serve as an interface when the interface is requested through theweb browser. For example, the web browser may serve as a mobile bankinginterface. The mobile banking interface may provide various bankingfunctions such as, for example, the ability to display a quantum ofvalue in one or more transfer records (e.g. display balances), configuretransfers of data (e.g. bill payments and other transfers), configurebudgeting tools, display a graphical user interface such as for examplea transfer record summary interface, and account management functions.

By way of further example, in at least some embodiments in which thecomputer device 300 functions as the computing device 110, theapplications 410 may include a spending summary application. Thespending summary application may be configured for secure communicationswith the server 120 and may display a graphical user interface such asfor example a transfer record summary interface provided by the server120.

By way of further example, in at least some embodiments in which thecomputer device 300 functions as the server 120, the applications 410may include an application configured for secure communications with anapplication programming interface (API). For example, the server 120 maybe configured to send, via the communications module and to the API, arequest for an image and may receive, via the communications module andfrom the API, the requested image.

When a user wishes to view past or previously-stored transfer recordswithin their account, the user may utilize an input interface (such as akeyboard and/or touchscreen) associated with the computing device 110 tocause the computing device 110 to open an application such as a mobilebanking application, a spending summary application or may cause thecomputing device 110 to open a webpage via a web browser. Touchgestures, for example, may be used. Once the application or webpage hasbeen opened on the computing device 110, the user may be required toenter authentication information such as for example a username andpassword. When the user has been authenticated, the computing device 110may display a graphical user interface (GUI) that includes at least oneselectable option which may be used to view past or previously-storedtransfer records. When the user selects the at least one selectableoption, a signal is sent to the server 120. The server 120 receives thesignal, via the communications module and from the computing device 110,and in response the server 120 performs a method.

FIG. 5 is a flowchart showing operations performed by the server 120according to an embodiment. The operations may be included in a method500 which may be performed by the server 120. For example,computer-executable instructions stored in memory of the server 120 may,when executed by one or more processors, configure the server 120 toperform the method 500 or a portion thereof.

The server 120 obtains transfer records associated with an account ofthe user (step 510). As mentioned, in this embodiment the user mayauthenticate using a username and a password. Once the user has beenauthenticated, the server 120 may obtain transfer records associatedwith the account of the user from the database. The transfer recordsidentify value transfers such as transactions made by the user. Eachtransfer record includes a transfer amount, a transfer date and atransfer descriptor. The transfer descriptor may include a name of amerchant and may include a location such as for example a city orcountry identifying where the transaction was initiated.

The server 120 may obtain all available transfer records associated withthe account of the user or may only obtain transfer records fortransactions made within the past six (6) months, one (1) year, two (2)years, five (5) years, etc.

The transfer records are grouped based on predefined criteria (step520). In this embodiment, the predefined criteria may include a defaultsetting. The default setting may be adjusted by the user.

In this embodiment, the transfer records are grouped based on the dateof the transaction. For example, transfer records may be grouped by day,week, month or year. In this embodiment, the predefined criteria groupsthe transfer records based on month. Put another way, transfer recordsreflecting value transfers made within the same month are groupedtogether. Other examples of predefined criteria may be based on alocation identified by the transfer descriptor.

Within at least one group of transfer records, one or morerepresentative transfer records are identified based at least on storedselection criteria (step 530).

In this embodiment, the stored selection criteria may be based on thetransfer amount, the transfer descriptor, and/or the date of thetransaction. For example, all transfer records within a group may becompared to one another, and the transfer record having the highesttransfer amount may be selected as a representative transfer record forthat group.

The stored selection criteria may identify one or more representativetransfer records as being interesting and may identify the interestingtransfer record as being the representative transfer record. Aninteresting transfer record may be a transfer record that the user islikely to find interesting. An interesting transfer record may beidentified based on one or more of the transfer amount, the transferdescriptor and the date of the transaction.

For example, all transfer records within a group may be compared to oneanother, and the transfer record that includes a transfer descriptoridentifying an interesting merchant or location may be selected as arepresentative transfer record for that group. The interesting locationor merchant may be a popular restaurant. To identify the interestinglocation or merchant, the server 120 may determine that transferdescriptor identifies a restaurant. To determine if the restaurant is apopular restaurant, the server 120 may send a request to the APIrequesting, for example, a number of images available for thatrestaurant. When the API responds with the number of images, the server120 may determine that the restaurant is a popular restaurant when thenumber of images exceeds a threshold. When more than one transfer recordwithin the group includes a transfer descriptor that identifies arestaurant, the server 120 may send a request to the API for eachtransfer record that includes a transfer descriptor that identifies arestaurant and may select the transfer record corresponding to therestaurant with the greatest number of images as being therepresentative transfer record for the group. Other examples ofinteresting locations or merchants include sporting venues, luxuryshops, bars, nightclubs, tourist attractions, theme parks, etc.

The API may additionally or alternatively determine that a particularlocation or merchant is popular or interesting based on a number ofsocial media interactions for an account of the particular location ormerchant. For example, the API may view a social media account of theparticular location or merchant and may obtain information indicating anumber of followers or interactions made within the social media networkfor that particular location or merchant.

The server 120 may tag at least one of the transfer records with a tagbased on a location or merchant identified by the transfer descriptorincluded in the at least one transfer record. For example, the server120 may tag transfer records that include transfer descriptorsidentifying locations or merchants located outside of a home city,province, state or country of the user. In this example, the server 120may determine the location of the user's home based on stored identitydata associated with the account of the user. When one or more transferrecords indicate locations or merchants located outside of, for example,the home country of the user, these transfer records may be tagged basedon the location. For example, when a user is travelling abroad and oneor more transfer records include transfer descriptions identifyingtransfers initiated at locations or merchants located in Paris, France,these transfer records may be tagged with “Paris” or “Paris, France.”The one or more transfer records tagged with “Paris” or “Paris, France”may be identified as the one or more representative transfer records forthe group.

The server 120 may tag at least one of the transfer records with a tagbased on a category of the merchant or location identified by thetransfer descriptor. For example, where a transfer record identifies amerchant that is a grocery store, a tag such as “Groceries” or “GroceryStore” may be assigned to the transfer record. Other examples of tagsinclude “Coffee Shop”, “Restaurant”, etc.

The server 120 may ignore some transfer records when identifying one ormore representative transfer records for the group. For example,transfer records that include transfer descriptors identifying locationsor merchants that may be associated with negative events may be ignored.Examples of locations or merchants that may be associated with negativeevents include health care centers (hospitals, clinics, etc.),pharmacies, veterinarian clinics, car repair centers, etc. Otherexamples of locations or merchants records that may be ignored includemembership fees, gas stations, etc. As mentioned, transfer records maybe assigned a tag by the server 120 and as such transfer records taggedwith particular tags may be ignored by the server 120.

The server 120 may identify one or more transfer records as being theone or more representative transfer records based on the date. Forexample, transfer records indicating a transaction made on a particularday such as on a weekend may be identified as the one or morerepresentative transfer records. As another example, transfer recordsindicating transactions made on the user's birthday or on a nationalholiday may be identified as the one or more representative transferrecords.

The server 120 obtains an image associated with at least one of therepresentative transfer records (step 540).

In this embodiment, the server 120 may obtain the image an image librarystored on the computing device 110, may obtain the image from the API,or may obtain the image from memory.

FIG. 6 is a flowchart showing operations performed by the server 120 inobtaining the image from an image library stored on the computing device110. The operations may be included in a method 600 which may beperformed by the server 120. For example, computer-executableinstructions stored in memory of the server 120 may, when executed byone or more processors, configure the server 120 to perform the method600 or a portion thereof.

The server 120 obtains permission to access the image library (step610).

In this embodiment, the server 120 sends, via the communications moduleand to the computing device 110, a signal requesting permission toaccess the image library associated with the computing device 110. Thesignal may cause the computing device 110 to display a messagerequesting access to the image library. The message may include one ormore selectable options to accept or deny the request. The server 120receives permission when a signal is received, via the communicationmodule, indicating that the user has accepted the request.

It will be appreciated that the server 120 may have previously obtainedpermission to access the image library. As such, in response to thecomputing device 110 receiving the signal requesting access to the imagelibrary, the server 120 may receive a signal, via the communicationsmodule and from the computing device 110, indicating that the server 120has permission to access the image library.

It will be appreciated that the image library may be stored in memory ofthe computing device 110 or may be stored in cloud storage and accessedthrough a network.

The server 120 selects an image from the image library and associatesthe image with the one or more representative data records (step 620).The server 120 stores the selected image in memory.

The metadata of the images in the image library may indicate a locationor merchant and/or a date of when the image was taken. As such, in thisembodiment, the server 120 compares the one or more representativetransfer records to metadata associated with images in the imagelibrary. For example, the metadata of one or more of the images in theimage library may identify a location that corresponds to a locationidentified by the transfer descriptor of the one or more representativetransfer records and one of these images is obtained by the server 120.When the merchant is a restaurant, the obtained image may be an imagetaken when the user was at the restaurant. The image may be a picture offood ordered at the restaurant, a picture of the user at the restaurant,etc.

As another example, the metadata of one or more of the images in theimage library may identify a location that corresponds to a tag of oneor more of the transfer records and one of these images is obtained bythe server 120. As mentioned above, the tag for the one or more transferrecords may be “Paris” or “Paris, France” and as such the server 120 mayobtain an image from the image library that has metadata indicating thatthe image was taken in “Paris” or “Paris, France”.

FIG. 7 is a flowchart showing operations performed by the server 120 inobtaining the image from the API. The operations may be included in amethod 700 which may be performed by the server 120. For example,computer-executable instructions stored in memory of the server 120 may,when executed by one or more processors, configure the server 120 toperform the method 700 or a portion thereof.

The server 120 sends, via the communications module and to the API, asignal requesting an image (step 710). The signal includes informationsuch as the tag, location or merchant of which the image is to beobtained.

For example, the server 120 may identify a location or merchant based onthe transfer descriptor of the one or more representative transferrecords. The signal sent to the API may include information regardingthe identified location or merchant, such as the name of a restaurant,etc.

In response to receiving the signal, the API obtains the requestedimage. For example, where the signal includes information regarding theidentified merchant, the API may obtain an image of the merchant, animage of a logo associated with the merchant, an image of an itemoffered by the merchant, an image based on a type of the merchant or animage based on a location of the merchant.

As mentioned, the signal may include information such as the tag. Forexample, the tag may be “Paris” or “Paris, France”. As such, the API mayobtain an image associated with “Paris” or “Paris, France.”

The server 120 receives, via the communications module and from the API,the image (step 720). The server 120 associates the received image withthe one or more representative transfer records and stores the receivedimage in memory.

It will be appreciated that in some embodiments, an image cannot befound for a particular representative transfer record. FIG. 8 is aflowchart showing operations performed by the server 120 in determiningthat an image cannot be found for a particular representative transferrecord. The operations may be included in a method 800 which may beperformed by the server 120. For example, computer-executableinstructions stored in memory of the server 120 may, when executed byone or more processors, configure the server 120 to perform the method800 or a portion thereof.

The server 120 determines that an image cannot be found for a particularone or more representative transfer records (step 810). For example, theimage library may not have an image that has metadata that correspondsto the one or more particular transfer records. As another example, theAPI may send a signal indicating that the requested image cannot befound.

In response to determining that an image cannot be found, the server 120removes the particular transfer record as being representative for thegroup (step 820).

The server then identifies another one or more data representativetransfer records with the group of transfer records (step 830). It willbe appreciated that the one or more representative transfer records isidentified in a manner similar to that described above with reference tostep 530. Of course, the particular one or more transfer records thatthe server 120 was not able to obtain an image for are no longereligible to be selected as the one or more representative transferrecords.

The server 120 may retrieve the image from memory. For example, theserver 120 may have previously obtained an image for a particularrepresentative transfer record and stored the image in memory. This mayreduce the computer processing power and bandwidth required to generatethe transfer record summary interface as previously obtained images maybe easily retrieved by the server 120.

As mentioned, the server 120 may obtain the image from memory, from theimage library stored on the computing device 110 or may obtain the imagefrom the API. The server 120 may attempt to (first) obtain the imagefrom memory. When no image is available from memory, the server 120 mayattempt to obtain the image from the image library stored on thecomputing device 110. When no image is available within the imagelibrary stored on the computing device 110, the server 120 may obtainthe image from the API. Alternatively, when no image is available inmemory, the server 120 may attempt to obtain the image from the API.When no image is available from the API, the server 120 may obtain theimage from the image library stored on the computing device 110. Asanother example, the server 120 may not have permission to access theimage library stored on the computing device 110 and as such must obtainthe image from the API. In some embodiments, when the server 120 cannotobtain an image from memory, cannot obtain an image from the imagelibrary stored on the computing device 110 and cannot obtain an imagefrom the API, a default image may be used. Alternatively, when theserver 120 cannot obtain an image from memory, cannot obtain an imagefrom the image library stored on the computing device 110 and cannotobtain an image from the API, a different representative data record maybe selected as described with reference to method 800.

As mentioned, when the image is obtained by the server 120, either fromthe image library stored on the computing device 110 or the API, theserver 120 associates the image with the one or more representativetransfer records and stores the obtained image in memory.

The server 120 sends, via the communications module and to the computingdevice 110, a transfer record summary interface (step 550). The transferrecord summary interface is a GUI and includes the image associated withthe at least one representative transfer record. The transfer recordsummary interface allows for communication with the server 120. Thetransfer record summary interface, when received by the computing device110, is displayed on the computing device 110. The transfer recordsummary interface may be displayed within the mobile application orwebpage described above.

The server 120 generates a graphical user interface (referred to as atransfer record summary interface) that provides a simple visualrepresentation of transfer records identifying value transfersassociated with an account of the user. The graphical user interfaceincludes an accurate visual representation of each group of transferrecords. The graphical user interface reduces the computer processingpower and bandwidth required to review or access transfer records as theuser is able to easily select a group of transfer records based on asingle representative image of the group. The graphical user interfaceis generated by the system in real time and as such the most recenttransfer records are included when generating the transfer recordsummary interface. Since images are obtained only for representativetransfer records, the processing power and bandwidth required togenerate the graphical user interface is reduced.

An example transfer record summary interface 900 is shown in FIG. 9. Thetransfer record summary interface 900 includes images 910 associatedwith at least one representative transfer record for transfer recordsgrouped based on the date of the transaction, specifically, transferrecords grouped by month. Although only the months of June, July andAugust are shown in FIG. 9, it will be appreciated that additionalmonths are included with the transfer record summary interface 900 andmay be viewed by the user by manipulating a slider 920. The user maymanipulate the slider using, for example, gestures such as touch inputon a display screen of the computing device 110.

In the example transfer record summary interface 900, the one or morerepresentative transfer records for the month of June may have beenidentified based on the transfer descriptor of the one or more transferrecords identifying a location or merchant associated with purchasingbaseball tickets or attending a baseball game. As such, the imageassociated with the at least one representative transfer record is animage based on baseball. For the month of July, the one or morerepresentative transfer records may have been identified based ontransfer records tagged “Paris” or “Paris, France” and as such the imageassociated with the at least one representative transfer record is animage of the Eiffel Tower. For the month of August, the one or morerepresentative transfer records may have been identified based on atransfer record having a transfer descriptor identifying a popularrestaurant and as such the image associated with the at least onerepresentative transfer record is an image of the restaurant.

Each image 910 may be selected by the user to obtain additionalinformation regarding the group of which the image is associated. Forexample, the user may select one of the images 910 via touch input onthe display screen of the computing device 110 to obtain additionalinformation regarding the group of which the image is associated.

FIG. 10 is a flowchart showing operations performed by the server 120 inproviding additional information regarding the group of which theselected image is associated. The operations may be included in a method1000 which may be performed by the server 120. For example,computer-executable instructions stored in memory of the server 120 may,when executed by one or more processors, configure the server 120 toperform the method 1000 or a portion thereof.

In response to the user selecting one of the images 910, the server 120receives, via the communications module and from the computing device110, a signal indicating that that the user has selected the image 910within the transfer record summary interface 900 (step 1010). The signalidentifies which image 910 is selected. Put another way, the signalidentifies which group of transfer records the selected imagerepresents.

The server 120 obtains all transfer records for the group represented bythe selected image 910, and sends, via the communications module and tothe computing device 110, a signal including all transfer records forthe group represented by the selected image (step 1020).

The computer processing power and bandwidth required by the server 120is reduced since all transfer records for a group are only obtained andprovided to the user when the user selects the image representing thegroup. Put another way, the server 120 is only required to provide alltransfer records for a group when requested by the user.

The transfer record summary interface displays, on the display screen ofthe computing device 110, all transfer records for the group representedby the selected image 910. An example is shown in FIG. 11 where aselected image 1110 is highlighted within the transfer record summaryinterface 900. All transfer records for the group represented by theselected image 1110, specifically the month of July, are displayed belowthe images 910. In this embodiment, the transfer records are displayedas a list of transfer records 1120. The list of transfer records 1120 issorted by date. Transfer records that correspond to foreigntransactions, that is, transfer records that required a foreign currencyexchange, are marked with an indicia 1130. It will be appreciated thatwhile all transfer records are available to be viewed by the user, onlya number of transfer records may be viewed at a given time due to thesize of the display screen of the computing device 110. Additionaltransfer records may be viewed by the user by manipulating a slider1140. The user may manipulate the slider using, for example, gesturessuch as touch input on the display screen of the computing device 110.

Each transfer record in the list of transfer records 1120 may beselected by the user to obtain additional information regarding thatparticular transfer record. As shown in FIG. 12, the user may select oneof the transfer records 1210 via touch input on the display screen ofthe computing device 110 to obtain additional information regarding theselected transfer record 1210. The selected transfer record 1210 may behighlighted.

In response to one of the transfer records 1210 being selected, thetransfer record summary interface 900 displays the additionalinformation regarding the selected transfer record 1120. An example isshown in FIG. 13. As can be seen, additional information 1310 isdisplayed below the selected transfer record 1210. The additionalinformation 1310 includes the location of the transaction and foreigncurrency exchange information (if required). The transfer descriptoridentifying the location or merchant associated with the transactioncontinues to be displayed.

In another embodiment, rather than displaying the additional informationfor all transfer records within a group as a list of transfer records,images associated with one or more representative transfer records forsub-groups within the group may be displayed. An example is shown inFIG. 14. As can be seen, a selected image 1410 is highlighted within thetransfer record summary interface 900. Data for all transfer records ofthe group represented by the selected image 1410, specifically the monthof July, are displayed below the images. In this embodiment, the data isdisplayed such that images associated with one or more representativetransfer records within sub-groups (of the group of which image 1410 isassociated) are shown. In this example, selected image 1410 represents agroup of transfer records for a particular month, July. As such, images1420 are shown which represent groups of transfer records for particularweeks (or sub-groups) within the month of July. It will be appreciatedthat when one of the images 1420 is selected, additional information fortransfer records within that week may be displayed. The additionalinformation may be in the form of a list of transfer records (similar toFIG. 11) or may be images associated with one or more representativetransfer records for sub-groups (in this case, days) within the group(week). The server 120 may obtain images for each sub-group in a mannersimilar to that described above and this may be done when a particularimage (such as image 1410) is selected or may be done prior to theserver 120 sending the transfer record summary interface to thecomputing device 110.

By providing images for each sub-group, the computer processing powerrequired by the server 120 is reduced as the server 120 is not requiredto obtain all transfer records for the group. Rather, the server 120 isonly required to provide an image for representative transfer records ofeach sub-group. The server 120 is only required to provide all transferrecords for the sub-group when requested by the user, for example, whenthe user selects the image representing the sub-group.

As mentioned, the predefined criteria used to group the transfer recordsmay be a default setting. The default setting or criteria may beadjusted by the user. An example transfer record summary interface 1500is shown in FIG. 15. Transfer record summary interface 1500 is similarto transfer record summary interface 900 with the following exception.In this embodiment, the transfer record summary interface 1500 includesa selectable option 1510 to update the criteria defining how thetransfer records are grouped.

In this embodiment, the selectable option 1510 is in the form of a dropdown menu. When selected via touch input on the display screen of thecomputing device 110, the selectable option 1510 displays a number ofoptions defining how the transfer records are to be grouped. The optionsmay include by day, week, month or year. In response to the useradjusting or selecting a different criteria, the server 120 may performa method to generate an updated transfer record summary interface.

FIG. 16 is a flowchart showing operations performed by the server 120 ingenerating an updated transfer record summary interface. The operationsmay be included in a method 1600 which may be performed by the server120. For example, computer-executable instructions stored in memory ofthe server 120 may, when executed by one or more processors, configurethe server 120 to perform the method 1600 or a portion thereof.

The server 120 receives, via the communication module and from thecomputing device 110, a signal indicating that the user has adjusted thecriteria (step 1610). As mentioned, in this embodiment the signal isreceived in response to the user selecting a different criteria usingselectable option 1510.

The server 120 groups the transfer records based on the updatedpredefined criteria (step 1620). As an example, the transfer records maybe currently grouped by month and the updated criteria may request thatthe transfer records be grouped by week. As such, the server 120 groupsthe transfer records by week. Put another way, transfer recordsreflecting transactions made within the same week are grouped together.

Within at least one group of transfer records, the server 120 identifiesone or more representative transfer records (step 1630). The server 120identifies one or more representative transfer records in a mannersimilar to step 530 described above.

For at least one representative transfer record that does not have anassociated image, obtain an image (step 1640). The server 120 identifiesrepresentative transfer records that do not already have an associatedimage. For example, the server 120 may determine that a particularrepresentative transfer record does not have an associated image storedin memory. As such, an image associated with each representativetransfer record that does not have already have an associated image isobtained in a manner similar to step 1640 described above.

The server 120 sends an updated transfer record summary interface thatincludes the obtained image (step 1650).

An example transfer record summary interface 1700 is shown in FIG. 17.As can be seen, transfer record summary interface 1700 is similar totransfer record summary interface 1500, however the transfer records aregrouped by week (rather than by month).

Similar to embodiments described above, the user may select an image toview data for all transfer records within the group represented by theselected image. An example is shown in FIG. 18. As can be seen, a listof transfer records 1810 for all transfer records of the grouprepresented by selected image 1820.

As can be seen in the list of transfer records 1810, the user had anumber of large transactions. For example, on July 15 the user spent$250.00 at a grocery store and $225.00 on a website that relates togolf. On July 18, the user spent $450.00 at a car repair center. Whenselecting one or more representative transfer records for the group, theserver 120 ignores the transfer record representing the transaction madeat the grocery store and the transfer record made at the car repaircenter. As such, the representative transfer record is selected as thetransfer record representing the transaction made at the website thatrelates to golf and the image 1820 associated with the representativetransfer record is an image of a golf club.

Although in embodiments described above, selectable options are used toscroll through various groups and selectable options are used to selectcriteria of which to group transfer records by, alternative inputs maybe used. For example, when transfer records are grouped by month (seefor example transfer record summary interface 900 of FIG. 9), the usermay wish to group transfer records by week. To adjust the criteria, theuser may perform a zoom-in gesture via touch input on the display screenof the computing device 110. In response to the zoom-in gesture, thecomputing device 110 may send a signal to the server 120 indicating thatthe transfer records are to be grouped by week. Similarly, when transferrecords are grouped by month (see for example transfer record summaryinterface 900 of FIG. 9), the user may wish to group transfer records byyear. To adjust the criteria, the user may perform a zoom-out gesturevia touch input on the display screen of the computing device 110. Inresponse to the zoom-out gesture, the computing device 110 may send asignal to the server 120 indicating that the transfer records are to begrouped by year. Zoom-in and zoom-out gestures may switch or togglebetween the various criteria. As mentioned, the various criteria may bedaily (most specific), weekly, monthly, yearly (least specific). Eachtime a zoom-in gesture is identified, the transfer records may be sortedby the next-most specific criteria. Similarly, each time a zoom-outgesture is identified, the transfer records may be sorted by thenext-least specific criteria.

Although transfer records are described as including a transferdescriptor that identifies a merchant or a location, those skilled inthe art will appreciate that the transfer descriptor may additionally oralternatively include information regarding items purchased. Forexample, when transfer is initiated at a clothing store, the transferdescriptor may include a list of all items purchased at the clothingstore. When the transfer record including the transfer descriptor thatincludes a list of all items purchased at the clothing store isidentified as being the representative transfer record for the group, animage of one of the purchased items may be obtained via the API. Forexample, an image of a particular article of clothing that was purchasemay be obtained via the API and set as the image associated with therepresentative transfer record.

In one or more embodiments, the user may create their own group oftransfer records. For example, the server 120 may provide, to thecomputing device 110, all transfer records for a particular month. Theuser may manually select one or more of these transfer records as agroup and may assign their own image to the manually selected group. Ofcourse, the server 120 may obtain an image for the manually selectedgroup similar to embodiments described above. In this manner, a user maycreate groups of transfer records associated with particular events suchas vacations.

The methods described above may be modified and/or operations of suchmethods combined to provide other methods.

Furthermore, the description above generally describes operations thatmay be performed by a server and a client device in cooperation with oneanother. Operations that are described as being performed by the servermay, instead, be performed by the client device.

Example embodiments of the present application are not limited to anyparticular operating system, system architecture, mobile devicearchitecture, server architecture, or computer programming language.

It will be understood that the applications, modules, routines,processes, threads, or other software components implementing thedescribed method/process may be realized using standard computerprogramming techniques and languages. The present application is notlimited to particular processors, computer languages, computerprogramming conventions, data structures, or other such implementationdetails. Those skilled in the art will recognize that the describedprocesses may be implemented as a part of computer-executable codestored in volatile or non-volatile memory, as part of anapplication-specific integrated chip (ASIC), etc.

As noted, certain adaptations and modifications of the describedembodiments can be made. Therefore, the above discussed embodiments areconsidered to be illustrative and not restrictive.

What is claimed is:
 1. A server comprising: a communications module; aprocessor coupled with the communications module; and a memory coupledto the processor and storing processor-executable instructions which,when executed by the processor, configure the processor to: obtaintransfer records identifying value transfers associated with an accountof a user, the transfer records including a transfer amount, a transferdate and a transfer descriptor; group the transfer records based onpredefined criteria; within at least one group of the transfer records,identify one or more representative transfer records based at least onstored selection criteria; obtain an image associated with at least oneof the representative transfer records; and send, via the communicationsmodule and to a computing device associated with the user, a transferrecord summary interface, the transfer record summary interfaceincluding the image associated with the at least one representativetransfer record.
 2. The server of claim 1, wherein the image is obtainedfrom one of the memory of the server, an application programminginterface (API) and an image library stored on the computing device. 3.The server of claim 2, wherein the image is obtained from the imagelibrary stored on the computing device and the processor-executableinstructions, when executed by the processor, further configure theprocessor to: obtain permission to access the image library stored onthe computing device; and associate one of the images within the imagelibrary to one of the representative transfer records based on acomparison of the representative transfer record and metadata of theassociated image.
 4. The server of claim 1, wherein theprocessor-executable instructions, when executed by the processor,further configure the processor to: receive, via the communicationsmodule and from the computing device, a signal indicating a selection ofone of the images; obtain all transfer records for the group representedby the selected image; and send, via the communications module and tothe computing device, all transfer records for the group represented bythe selected image.
 5. The server of claim 4, wherein theprocessor-executable instructions, when executed by the processor,further configure the processor to: tag at least one of the transferrecords with a tag based on the transfer descriptor; and obtain theimage based on the tag.
 6. The server of claim 4, wherein theprocessor-executable instructions, when executed by the processor,further configure the processor to: for at least one representativetransfer record, identify a merchant based on the transfer descriptor;and obtain the image associated with the at least one representativetransfer record based at least on the identified merchant, the imageincluding at least one of an image of the merchant, an image of a logoassociated with the merchant, an image of an item offered by themerchant, an image based on a type of the merchant or an image based ona location of the merchant.
 7. The server of claim 1, wherein theprocessor-executable instructions, when executed by the processor,further configure the processor to: determine that an image cannot beobtained for a particular representative transfer record; remove theparticular representative transfer record as being the representativetransfer record for a particular group of transfer records; and identifyanother transfer record as being representative for the particular groupof transfer records based at least on the stored selection criteria. 8.The server of claim 1, wherein the transfer record summary interfaceincludes an option to adjust the predefined criteria and theprocessor-executable instructions, when executed by the processor,further configure the processor to: receive, via the communicationsmodule and from the computing device, a signal indicating that the userhas adjusted the predefined criteria; group transfer records based onthe updated predefined criteria; within at least one group of transferrecords, identify one or more transfer records as being representativebased at least on the stored selection criteria; for at least onerepresentative transfer record that does not have an associated image,obtain an image; and send, via the communications module and to thecomputing device associated with the user, an updated transfer recordsummary interface, the updated transfer record summary interfaceincluding the image associated with the at least one representativetransfer record.
 9. The server of claim 1, wherein the predefinedcriteria includes a particular period of time.
 10. The server of claim1, wherein the stored selection criteria includes at least one of thetransfer amount or the transfer descriptor.
 11. A method comprising:obtaining transfer records identifying value transfers associated withan account of a user, the transfer records including a transfer amount,a transfer date and a transfer descriptor; grouping the transfer recordsbased on predefined criteria; within at least one group of the transferrecords, identifying one or more representative transfer records basedat least on stored selection criteria; obtaining an image associatedwith at least one of the representative transfer records; and sending,via a communications module and to a computing device associated withthe user, a transfer record summary interface, the transfer recordsummary interface including the image associated with the at least onerepresentative transfer record.
 12. The method of claim 11, wherein theimage is obtained from one of a memory of a server, an applicationprogramming interface (API) and an image library stored on the computingdevice.
 13. The method of claim 12, wherein the image is obtained fromthe image library stored on the computing device and the method furthercomprises: obtaining permission to access the image library stored onthe computing device; and associating one of the images within the imagelibrary to one of the representative transfer records based on acomparison of the representative transfer record and metadata of theassociated image.
 14. The method of claim 11, further comprising:receiving, via the communications module and from the computing device,a signal indicating a selection of one of the images; obtaining alltransfer records for the group represented by the selected image; andsending, via the communications module and to the computing device, alltransfer records for the group represented by the selected image. 15.The method of claim 14, further comprising: tagging at least one of thetransfer records with a tag based on the transfer descriptor; andobtaining the image based on the tag.
 16. The method of claim 14,further comprising: for at least one representative transfer record,identifying a merchant based on the transfer descriptor; and obtainingthe image associated with the at least one representative transferrecord based at least on the identified merchant, the image including atleast one of an image of the merchant, an image of a logo associatedwith the merchant, an image of an item offered by the merchant, an imagebased on a type of the merchant or an image based on a location of themerchant.
 17. The method of claim 11, further comprising: determiningthat an image cannot be obtained for a particular representativetransfer record; removing the particular representative transfer recordas being the representative transfer record for a particular group oftransfer records; and identifying another transfer record as beingrepresentative for the particular group of transfer records based atleast on the stored selection criteria.
 18. The method of claim 11,wherein the transfer record summary interface includes an option toadjust the predefined criteria and the method further comprises:receiving, via the communications module and from the computing device,a signal indicating that the user has adjusted the predefined criteria;grouping transfer records based on the updated predefined criteria;within at least one group of transfer records, identifying one or moretransfer records as being representative based at least on the storedselection criteria; for at least one representative transfer record thatdoes not have an associated image, obtaining an image; and sending, viathe communications module and to the computing device, an updatedtransfer record summary interface, the updated transfer record summaryinterface including the image associated with the at least onerepresentative transfer record.
 19. The method of claim 11, furthercomprising: wherein the stored selection criteria includes at least oneof the transfer amount and the transfer descriptor.
 20. A non-transitorycomputer readable storage medium comprising computer-executableinstructions which, when executed, configure a processor to: obtaintransfer records identifying value transfers associated with an accountof a user, the transfer records including a transfer amount, a transferdate and a transfer descriptor; group the transfer records based onpredefined criteria; within at least one group of the transfer records,identify one or more representative transfer records based at least onstored selection criteria; obtain an image associated with at least oneof the representative transfer records; and send, to a computing deviceassociated with the user, a transfer record summary interface, thetransfer record summary interface including the image associated withthe at least one representative transfer record.